Apparatus, systems and methods for deleting recording timers of a media device

ABSTRACT

Systems and methods are operable to manage timers that control recording of media content. An exemplary embodiment compares a retrieved stale timer criteria with a retrieved timer attribute; determines whether the timer is stale based on the comparison of the retrieved timer attribute and the stale timer criteria, wherein the timer is determined to be stale when the media content event identified by the timer will not be recorded because the media content event identified by the timer is not scheduled to be broadcast at a future date; and then automatically deletes the timer in response to determining that the timer is stale.

PRIORITY CLAIM

This application is a Continuation of U.S. application Ser. No.14/886,322, filed Oct. 19, 2015, granted as U.S. Pat. No. 9,596,503 onMar. 14, 2017, and entitled “APPARATUS, SYSTEMS AND METHODS FOR DELETINGRECORDING TIMERS OF A MEDIA DEVICE,” the contents of which isincorporated herein by reference in its entirety.

BACKGROUND

Media devices, such as a set top box, a stereo, a television, a computersystem, a game system, or the like, are configured to present a mediacontent event to a user. The video portion of the media content event ispresented to a user on a display and the audio portion of the mediacontent is reproduced as audible sounds by one or more speakers. In abroadcast operating environment, a media content provider broadcasts oneor more streams of media content (interchangeably referred to herein asa media content stream) to the media devices.

Typically, a media content event presents theme-based visual and audiocontent to a user for their enjoyment and/or for informative purposes.Examples of such theme-based content includes movies, films, serialprogramming, sporting events, documentaries, newscasts, religiousprograms, commercials (typically of short duration with advertisingcontent), or the like. Serial programming may present a continuing plotand/or theme, often with the same cast of actors, in a sequentialepisode-by-episode basis that is available periodically. Advertisements,commercials or the like may be interspersed within the media contentevent.

In a broadcast environment, the media content event is broadcast to aplurality of media devices in a stream of media content residing in themedia content stream. Typically, at any given instant in time, the mediadevice may be receiving one or more media content streams with hundredsof, or even thousands of, concurrently broadcast streaming media contentevents. Typically, presentation of a media content event occurs oversome time span (duration). Thus, the media content event has a beginningportion that usually presents identifying information about the mediacontent event, such as music, text of a title, or other information.When the user views this beginning portion of the media content event,the user intuitively understands that they are viewing the beginning ofthe media content event.

If the user is viewing a live broadcast of a particular media contentevent of interest, the media content event of interest is presented asit is being received by the media device. Accordingly, as a stream ofmedia content with the media content event of interest is beinginitially broadcast, presentation of the media content event of interestto the user can begin at the actual broadcast start time of the mediacontent event of interest. As time progresses, the entirety of thestreaming media content event of interest is presented to the user asthe stream of media content is being broadcast to and is received at themedia device. At some point, the media content event of interest comesto its end (conclusion).

On occasion, the user may be interested in viewing a particular mediacontent event that is scheduled for broadcasting at a future time. Aschedule of media content events and their associated broadcast scheduleis presented to the user in the form of an electronic program guide(EPG). The user typically is able to navigate to and highlight (focus)onto a region of the presented EPG that is indicating the particularmedia content event of interest that the user is interested in viewingand/or recording. For convenience, the user may specify, via thepresented EPG, a particular media content event of interest that shouldbe recorded (saved into a memory medium), such as a digital videorecorder residing in the media device.

In response to receiving the user specification for a recording of aparticular media content event, the media device accesses EPGinformation that includes the scheduled broadcast start time, thescheduled broadcast end time, and the channel that is providing thebroadcast of the specified media content event of interest. Thescheduled broadcast start time is used to define a recording start time(these times are typically the same time, though some amount of time maybe optionally added to advance the recording start time ahead of thescheduled broadcast start time by some predefined duration). Similarly,the scheduled broadcast end time is used to define a recording end time(these times are typically the same time, though some amount of time maybe optionally subtracted to delay the recording end time behind of thescheduled broadcast end time by some predefined duration). The mediacontent event identifier, recording start time, the recording end time,the channel identifier, and/or other recording instructions(interchangeably referred to herein as a “timer”) is then stored by themedia device.

The timer may specify recording information for a single media contentevent. In other instances, the timer may specify that the media deviceis to perform a plurality of recordings for a series of related mediacontent events. For example, the user may enjoy a comedy series, whereina new episode of the comedy is broadcast each week at a particular timeand on a particular channel during its episode season. The timers mayindicate that the media device is to record new broadcast episodes ofthe comedy series.

As time progresses, the media device compares real time with the starttimes of each of the stored timers. When real time approaches thebroadcast start time of a particular timer, the media device “tunes”itself to the channel that is broadcasting the specified media contentevent. The channel information of the timer is used to tune the mediadevice to receive the media content stream having the specified mediacontent event of interest.

Then, at the specified start time, the media device initiates recordingof the media content event. That is, the recording begins when real timereaches the scheduled broadcast time. The recording ends at thespecified end time (corresponding to the broadcast end time).

For each requested recording, a timer is generated. Accordingly, over arelatively long period of time, the user may request recordings of manydifferent media content events (or series of related media contentevents). Thus, many different timers may be stored by the media device.At some point in time, a timer is likely to become stale and no longerbe valid. That is, at some point in time, a stored timer will never beused again to record a media content event. Such timers areinterchangeably referred to herein as a “stale timer.”

For example, if the timer is configured to record a plurality of serialmedia content events (such as the example comedy series that weeklybroadcasts a new episode during its season), at some point it is likelythat the series will end. After the series finale has been broadcast,there will never be new broadcast media content events for thatparticular series. Thus, that timer will become stale (and never be usedagain). Similarly, a sporting event between two particular teams willoccur only one time. After the sporting event is broadcast, the timergenerated for the recording of the sporting event will never be usedagain, and thus will become a stale timer.

The accumulation of a large number of timers, and particularly a largenumber of stale times, at the media device creates several issues. Afirst issue is that storing a large number of timers at the media devicerequires a relatively large amount of memory storage capacity. Here, anystale timers stored in the memory unnecessarily utilize memory capacityof the media device.

A second issue arises in that some media devices must constantly comparereal time with the recording start times of each of the stored timers.Here, computational resources of the media device are needlessly used ifthe start times of stale timers are continually reviewed since the staletimers will never be used to generate an actual recording at the mediadevice.

A third issue arises when many timers have been stored and generated atthe media device. The user of the media device is typically responsiblefor management of their user-defined timers. The media device istypically configured to present the user a listing, menu, or the like oftheir user-defined timers. If a large number of timers have been definedby the user, then the process of reviewing their timers may berelatively cumbersome for the user (in that some amount of time will berequired for the user to review and ascertain the recording informationof each listed timer, and then make a decision to delete or retain eachparticular timer).

Further, if a timer is no longer desirable, or if a timer is stale, theuser may be required to manually instruct the media device to delete orotherwise erase that particular timer. If many stale timers are listed,the user amount of time required for the user to identify, consider, andthen to manually delete stale timers may be perceived by the user as awaste of their personal time.

Accordingly, there is a need in the arts to better manage timers thathave been stored at a media device.

SUMMARY

Systems and methods of managing timers that control recording of mediacontent are disclosed. An exemplary embodiment compares a retrievedstale timer criteria with a retrieved timer attribute; determineswhether the timer is stale based on the comparison of the retrievedtimer attribute and the stale timer criteria, wherein the timer isdetermined to be stale when the media content event identified by thetimer will not be recorded because the media content event identified bythe timer is not scheduled to be broadcast at a future date; and thenautomatically deletes the timer in response to determining that thetimer is stale.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred and alternative embodiments are described in detail below withreference to the following drawings:

FIG. 1 is a block diagram of an embodiment of a stale timer managementsystem implemented in a media device;

FIG. 2 conceptually illustrates information associated with a pluralityof active timers that are stored in the timer data portion of a memoryof the media device; and

FIG. 3 conceptually illustrates information associated with stale timercriteria that is stored in the memory of the media device.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of an embodiment of a stale timer managementsystem 100 implemented in a media device 102, such as, but not limitedto, a set top box (STB). Embodiments of the stale timer managementsystem 100 may be implemented in other media devices, such as, but notlimited to, a stereo, a surround-sound receiver, a radio, a television(TV), a digital video disc (DVD) player, a digital video recorder (DVR),a game playing device, or a personal computer (PC) that is configured toreceive a media content stream 104 having one or more media contentevents therein.

Embodiments of the stale timer management system 100 are configured toselectively delete, erase or otherwise discard stale timers.Accordingly, processing power of the media device 102 is conserved(since recording information associated with deleted stale timers are nolonger monitored and compared with real time), memory capacity at themedia device 102 is conserved (since selected stale timers areautomatically deleted), and user interaction for timer management isstreamlined (since the user does not have to manage stale timers thathave been automatically deleted).

In the various embodiments, when an active timer initially becomesstale, the stale timer is not immediately deleted. Rather, someattribute of a stale timer is compared with one or more stale timercriteria. If and when a stale timer attribute corresponds to (matcheswith) at least one stale timer criteria, then that particular staletimer is selectively deleted, erased or otherwise discarded from themedia device 102. The deleted, erased or otherwise discarded is referredto herein as a deleted stale timer.

The exemplary media device 102 is communicatively coupled to a mediapresentation system 106 that includes a visual presentation device 108,such as a television (hereafter, generically a TV), and an audiopresentation device 110, such as a surround sound receiver controllingan audio reproduction device. The video portion of the media contentevent is presented to a user on a display 112 of the visual presentationdevice 108. The audio portion of the media content is reproduced asaudible sounds by one or more speakers 113 of the audio presentationdevice 110. Other types of output devices may also be coupled to themedia device 102, including those providing any sort of stimuli sensibleby a human being, such as temperature, vibration and the like. In someembodiments, the media device 102 and one or more of the components ofthe media presentation system 106 may be integrated into a singleelectronic device.

The non-limiting exemplary media device 102 comprises a media contentstream interface 114, a processor system 116, a memory 118, a programbuffer 120, an optional digital video recorder (DVR) 122, a presentationdevice interface 124, a remote interface 126, and an optional networkinterface 128. The memory 118 comprises portions for storing the mediadevice logic 130, the electronic program guide (EPG) information 132, anoptional browser 134, timer data 136, timer manager logic 138, and staletimer criteria 140. In some embodiments, the media device logic 130 andthe timer manager logic 138 may be integrated together, and/or may beintegrated with other logic. Alternatively, or additionally, the EPGinformation 132, the timer data 136, and/or the stale timer criteria 140may be stored together and/or may be stored in any other suitable memorymedium In other embodiments, some or all of these memory and other datamanipulation functions may be provided using a remote server or otherelectronic devices suitably connected via the Internet or otherwise to aclient device. Other media devices 102 may include some, or may omitsome, of the above-described components. Further, additional componentsnot described herein may be included in alternative embodiments.

The functionality of the media device 102, here illustrated as a genericset top box, is now broadly described. In a satellite broadcast system,a media content provider provides media content that is received in oneor more multiple media content streams 104 multiplexed together in oneor more transport channels. The transport channels with the mediacontent streams 104 are communicated to the media device 102 from amedia system sourced from a remote head end facility (not shown)operated by the media content provider. The media device 102 isconfigured to receive one or more broadcasted satellite signals detectedby an antenna (not shown). Non-limiting examples of other media systemsthat broadcast a media content stream 104 include a cable system, aradio frequency (RF) communication system, and the Internet.

The one or more media content streams 104 are received by the mediacontent stream interface 114. In a broadcast environment, one or moretuners 142 in the media content stream interface 114 selectively tune toone of the media content streams 104 in accordance with instructionsreceived from the processor system 116. The processor system 116,executing the media device logic 130 and based upon a request for amedia content event of interest specified by a user, parses out mediacontent associated with the media content event of interest. The mediacontent event of interest is then assembled into a stream of videoand/or audio information which may be temporarily stored (buffered) bythe program buffer 120 such that the media content can be streamed outto components of the media presentation system 106, such as the visualdisplay device 108 and/or the audio presentation device 110, via thepresentation device interface 124.

Alternatively, or additionally, the parsed out media content event maybe saved into the DVR 122 for later presentation. The DVR 122 may bedirectly provided in, locally connected to, or remotely connected to,the media device 102. The recording of a received media content event iscontrolled by the media device logic 130 in accordance with anassociated timer 144 that has been stored in the timer data 136. Thetimer 144 is predefined by the media device 102 based on a recordingrequest made by a user of the media device 102. The timer 144 includes amedia content event identifier, recording start time, the recording endtime, the channel identifier, and/or other recording instructions of themedia content event that is to be recorded.

From time to time, information populating the EPG information 132 of thememory 118 is communicated to the media device 102, via the mediacontent stream 104 or via another suitable media. The EPG information132 stores the information pertaining to the scheduled programming ofmedia content events. The EPG information 132 may include, but is notlimited to, an identifier, a scheduled presentation start and/or endtime, a program channel, and descriptive information for each mediacontent event. The media content event's descriptive information mayinclude the title of the media content event, names of performers oractors, date of creation, and a summary describing the nature of themedia content event. Any suitable information may be included in thesupplemental information. Upon receipt of a command from the userrequesting presentation of an EPG display, the information in the EPGinformation 132 is retrieved, formatted, and then presented on thedisplay 112 as an EPG 146.

The exemplary media device 102 is configured to receive commands from auser via a remote control 148. The remote control 148 includes one ormore controllers 150 disposed on the surface of the remote control 148.The user, by actuating one or more of the controllers 150, causes theremote control 148 to generate and transmit commands, via a wirelesssignal 152, to the media device 102. The commands control the mediadevice 102 and/or control the various components of the mediapresentation system 106. The wireless signal 152 may be an infrared (IR)signal or a radio frequency (RF) signal that is detectable by the remoteinterface 126.

The processes performed by the media device 102 relating to theprocessing of the received media content stream 104 and communication ofa presentable media content event to the components of the mediapresentation system 106 are generally implemented by the processorsystem 116 while executing the media device logic 130. Thus, the mediadevice 102 may perform a variety of functions related to the processingand presentation of one or more media content events received in themedia content stream 104.

Some embodiments of the media device 102 may be configured tocommunicatively couple to a remote timer management system 154 to whichthe network interface 128 is coupled, via a communication system 156.The communication system 156 is illustrated as a generic communicationsystem. In one embodiment, the communication system 156 comprises acellular telephone system, such as a radio frequency (RF) wirelesssystem. Accordingly, the media device 102 includes a suitabletransceiver. Alternatively, the communication system 156 may be atelephony system, the Internet, a Wi-fi system, a microwavecommunication system, a fiber optics system, an intranet system, a localaccess network (LAN) system, an Ethernet system, a cable system, a radiofrequency system, a cellular system, an infrared system, a satellitesystem, or a hybrid system comprised of multiple types of communicationmedia. Additionally, embodiments of the media device 102 may beimplemented to communicate using other types of communicationtechnologies, such as but not limited to, digital subscriber loop (DSL),X.25, Internet Protocol (IP), Ethernet, Integrated Services DigitalNetwork (ISDN) and asynchronous transfer mode (ATM). Also, embodimentsof the media device 102 may be configured to communicate overcombination systems having a plurality of segments which employdifferent formats for each segment that employ different technologies oneach segment

FIG. 2 conceptually illustrates non-limiting example informationassociated with a plurality of timers 144 that are stored in the timerdata 136 of memory 118 (FIG. 1). In some embodiments, the recordinginformation (interchangeably referred to herein as “timer information”)stored in the timer data 136 is stored using a suitable database or thelike. Any suitable data storing format may be used by the variousembodiments. In some embodiments, the timer information is integratedwith the EPG broadcasting information stored in the EPG information 132.

The exemplary timer information of any particular timer 144 includesvarious information (interchangeably referred to herein as timerattributes) that is used to identify a media content event that is to berecorded into the DVR 122 when that particular identified media contentevent is broadcast to and is received at the media device 102. In someembodiments, the timers 144 may include less information, additionalinformation, and/or alternative information, than the exemplary timerinformation (timer attributes) shown in FIG. 2.

Each timer 144 includes at least one unique media content event (MCE)identifier, conceptually indicated in the “MCE Identifier” column 202(see for example “Program i”) that is used to identify a media contentevent that is to be recorded from other media content events. Anysuitable identifier may be used to identify a media content event thatis scheduled for presentation.

Channel information, conceptually indicated in the channel informationcolumn 204 (see “Station i” for the Program i, for example), identifiesthe “channel” that the media content event will be received on in themedia content stream 104. The channel information may be used for avariety of purposes. For example, the media device 102 may be receivingmany different media content streams 104, each broadcast at a particulardifferent frequency (or frequency range). The tuner 142 would use thechannel information to “tune” to the correct media content stream 104having the associated media content event that is to be recorded.Alternatively, or additionally, the channel information may indicate themedia content source (interchangeably referred to herein as a “station”)that originated the media content event. Alternatively, or additionally,the channel information may include other identifying information, suchas a packet identifier (PID) of the like that is used to identify datapackets that are transporting the media content event to the mediadevice. In some operating applications, several different media contentevents may be interleaved together into a single media content stream104. The PID information or the like is then used to parse out the mediacontent event that is being recorded from the other media content eventsreceived in the same media content stream 104.

Each timer 144 includes a start date, conceptually indicated in thestart date column 206 (see “S date i” for the Program i, for example).Each timer 144 also includes a start time, conceptually indicated in thestart time column 208 (see “S time i” for the Program i, for example).The start date identifies the date (month, day, year, or the like) andthe start time identifies the time of day that the media content eventis to be recorded. The start date and start time correspond to the dateand time that the media content event is scheduled to be broadcast tothe media device 102. In some embodiments, the start time may be offsetin advance of the broadcast start time by some relatively smallpredefined duration.

The media device 102 has an internal clock component (not shown), or hasaccess to real time information, that provide the current real time anddate. In an example embodiment, the real time and date is compared withthe start time and start date information in the various timers 144stored in the timer data 136. As the current real time and dateapproaches the scheduled broadcast date and time of one of the timers144, the media device 102 initiates the process of recording thatparticular associated media content event. In other embodiments, thereal time and date may be compared to the scheduled broadcast time anddate.

At some short duration prior to the start time (an/or scheduledbroadcast time), the media device 102 operates or configures one to itstuners 142 to receive the media content event from its designated mediacontent stream 104. As noted above, the tuner 142 then becomesconfigured (operational) to receive the designated media content stream104 based on the channel information. Then, the processor system 116 isable to receive and process the incoming media content stream 104. Whenthe broadcast of the media content event occurs (as specified in thestart date 206 and the start time 208, and/or as specified by thescheduled broadcast start time and date that is indicated in the EPGinformation 132), the DVR 122 begins to record the media content event.

Each timer 144 includes an end time, conceptually indicated in the endtime column 210 (see the “E time i” for the Program i, for example). Theend time corresponds to the scheduled broadcast end time of the mediacontent event. During the recording of the media content event, the endtime (and optionally the end date) are compared with real time. When theend time is reached, the recording process ends. In some embodiments,the start time may be offset to occur after the broadcast end time bysome relatively small predefined duration.

Timers 144 may include a flag or other indicator (conceptually indicatedin the “Reoccur” column 212) that indicates whether a media contentevent is one of a series of related media content events (such as theabove-described weekly comedy series). For example, the first mediacontent event (“Program 1”) indicates that that particular media contentevent is not a reoccurring type of media content event that should berepeatedly recorded when different serial episodes are broadcast (hereindicated by the “No” entry, though any suitable flag or indicia may beused). In contrast, the second media content event (“Program 2”) isindicated as being a reoccurring type media content event (hereindicated by the “Yes” entry, though any suitable flag or indicia may beused). Here, the media device 102 is configured to record a nextinstance of the reoccurring media content event when it is broadcast inthe future. In an example embodiment, the start date of the timer 144 isadvanced to the upcoming scheduled broadcast date of the next scheduledepisode. (Some embodiments of the media device 102 may be configured torecord only new episodes, and therefore conserve memory resources of theDVR 122.)

In some embodiments, the timers 144 may include optional informationthat indicates whether the timer 144 of the associated media contentevent has become stale or if the timer 144 is an active timer. A flag orother indicator (conceptually indicated in the “Stale” column 214) isused that indicates whether a media content event is active or stale.Here, an active timer is a timer 144 that will result in a recording ofa broadcasted media content event since the information of the activetimer corresponds to a media content event that is scheduled forbroadcast to the media device 102 (assuming that that particular mediacontent event is actually broadcast as scheduled, and is therefore notdelayed, preempted, or otherwise cancelled).

In contrast, a stale timer will never result in a recording (or at leasthave a very low probability that a recording will be made) since themedia content event associated with the stale timer is not scheduled forbroadcast. For example, a media content event associated with the staletimer may have already been broadcast. As another non-limiting example,the media content event associated with the stale time may be the lastof a series of media content events. Or, the media content eventassociated with the stale timer may have been delayed, preempted, orotherwise cancelled.

If the timer 144 of the associated media content event is not stale(here indicated by the “No” entry, though any suitable flag or indiciamay be used), then the media device 102 continually monitors thescheduled start date and start time for that particular timer 144 withthe current real time and date in anticipation that that particularmedia content event is to be recorded when it is being broadcast in oneof the media content streams 104. If the timer 144 of the associatedmedia content event is stale (here indicated by the “Yes” entry, thoughany suitable flag or indicia may be used), then one skilled in the artappreciates that no future broadcast of that particular media contentevent will occur, and therefore, that no recording will ever beinitiated based on that particular timer 144. In some embodiments, themedia device 102 continually monitors the scheduled start date and starttime of the stale timers with the current real time and date even thoughthat particular media content event will never be recorded (thusneedlessly utilizing computation resources of the media device 102 untilembodiments of the stale timer management system 100 delete the staletimer).

In some embodiments, the timer 144 may optionally include the title,conceptually indicated in the Title column 216 (see “Title i” for theProgram i, for example) of the media content event for that particulartimer 144. When the timer listing 158 (FIG. 1) is presented to the userto facilitate the user's management of their user-specified timers 144,the title may be retrieved and presented to the user so that the userintuitively appreciates which particular media content event is beingrecorded by that particular timer 144.

Miscellaneous information, conceptually indicated in the MiscellaneousInformation column 218 (see “Information i” for the Program i, forexample) of a timer 144 may include other information that may be ofinterest to a user when a timer listing 158 is generated and displayed.In an example embodiment, the miscellaneous information identifieswhether the associated media content event is provided on a premiumsubscription basis, and the identity of the providing the premiumservice. Typically, the user of a particular media device 102 must pay apremium service charge and obtain authorization information before theassociated media content vent can be viewed and/or recorded. Anysuitable information may be used by the various embodiments.

In the various embodiments, a particular stale timer may be deleted fromthe timer data 136 in a variety of manners. In an example embodiment,the user may manually delete any previously generated timer 144. Here,the user may personally know that a particular timer 144 is or willbecome stale, such as when a series has ended (or is ending) and is nolonger being produced.

In one exemplary embodiment, media content events scheduled forrecording are indicated on a presented EPG 146 with a suitable icon,lettering, and/or shading. The indicators intuitively inform a viewinguser that that particular media content event shown on the EPG 146 isscheduled for recording. A timer 144 has been previously generated basedon a received user request to record that particular media contentevent, and/or broadcasting episodes of a serial media content event thatis periodically broadcast. The user may manually navigate to the portionof the EPG 146 associated with a media content event scheduled forrecording, and then actuate one or more of the controllers 150 on theirremote control 148 to manually cause the associated timer 144 to bedeleted from the timer data 136. The presented EPG 146 may then bemodified to indicate that the recording has been manually canceled bythe user.

Alternatively, or additionally, a presented timer listing 158 indicatespreviously generated timers 144 to the viewing user. The timer listing158 may be configured to permit the user to select a particular timer144 for deletion. For example, if the user appreciates that a timer 144associated with a particular series of media content events has becomestale, the user may manually delete that particular stale timer 144 viathe presented timer listing 158. In an example embodiment, the timerlisting 158 may provide a graphical icon (such as a square, circle orthe like) that the user may navigate to and then select by actuation oneor more of the controllers 150 on their remote control 148.Alternatively, the user may navigate to a particular region of thepresented timer listing 158 to highlight a particular timer 144. Asubsequent actuation of one or more of the controllers 150 will thendelete that highlighted timer 144.

FIG. 3 conceptually illustrates information associated with stale timercriteria 300 that is stored in the stale timer criteria 140 of memory118 (FIG. 1). The non-limiting exemplary stale timer criteria 300include: a user specified generic stale timer activity duration 302, apredefined stale generic timer activity duration 304, user subscriptioninformation and/or authorization 306, predefined media contentinformation 308, and/or a predefined media content event identifier 310.Depending on the embodiment, some of the various stale timer criteriamay be combined, may be omitted, and/or other stale timer criteria maybe added.

In the various embodiments of the stale timer management system 100,information (timer attributes) pertaining to the timers 144 stored inthe timer listing 158 are compared to a corresponding stale timercriteria 300. If one or more timer attributes of a particular timer 144matches with (is the same, or corresponds to) a corresponding staletimer criteria 300, than that particular timer 144 is determined to be astale timer. The stale timer may then be automatically deleted from thetimer listing 158 by the stale timer management system 100.

The stale timer management system 100 may perform the comparison of thetimer information with the stale timer criteria 140 at various times. Inan example embodiment, the comparison is performed periodically based ona predefined duration. The user may define the duration. Alternatively,or additionally, the duration may be predefined by the media contentprovider or another interested entity. The duration may be stored in thememory 118 or another suitable memory medium, and then accessedaccordingly by the timer manager logic 138. For example, but not limitedto, the duration may be a week, a month or a year such that thecomparison is performed weekly, monthly, or annually. Any suitableduration may be used in the various embodiments.

Alternatively, or additionally, the comparison may be performed when theuser initially uses the media device 102 for presentation of a mediacontent event and/or to schedule a media content event for recording.Alternatively, or additionally, the comparison may be performed at apredefined specific date and/or time. Alternatively, or additionally,the comparison may be performed in response to some other event, such asa user account change and/or a change in subscriber services of theuser.

The first example stale timer criteria 300 is the user specified genericstale timer activity duration 302. Here, the user specifies a duration,such as one month, one year, or the like. Any suitable duration may bespecified. For any particular timer 144, if no recording activity hasoccurred at the media device 102 over that preceding user specifiedduration, then that particular timer 144 is determined to be a staletimer. Then, that determined stale timer is automatically deleted by thestale timer management system 100. Here, the user-specified duration ofinactivity is generically applicable to any stored timer 144 (and hence,the duration is named as the “user specified generic stale timeractivity duration 302”).

The second example stale timer criteria 300 is the predefined stalegeneric timer activity duration 304. Here, the media content provider oranother interested entity specifies a duration, such as one month, oneyear, or the like. Any suitable duration may be specified. For anyparticular timer 144, if no recording activity occurs at the mediadevice over that predefined duration, then that particular timer 144 isdetermined to be a stale timer. Then, that determined stale timer isautomatically deleted by the stale timer management system 100. Here,the predefined duration of inactivity is generically applicable to anystored timer 144 (and hence, the duration is named as the “predefinedstale generic timer activity duration 304”).

In an example embodiment, when the criteria 302 and/or 304 are used as abasis of comparison to determine if a timer 144 is stale and should beautomatically deleted, a difference is determined between the start dateand start time of a timer 144 and the current real date and time. If thedetermined difference is greater than or equal to (that is, at leastequal to) the user specified duration or the predefined duration, thenthe timer 144 is defined as a stale timer and is then automaticallydeleted by the stale timer management system 100. That is, if the actualduration of inactivity is greater than or equal to the user defined orpredefined duration, the timer 144 is deleted. It is appreciated thatunder this scenario, some timer 144 may actually be stale timers, butare not yet automatically deleted by the stale timer management system100 since the duration of inactivity is not yet greater than or equal tothe user defined or predefined duration attribute of the timer 144.

Some serial type media content events are characterized by a pluralityof episodes that are broadcast over a particular duration (referred tointerchangeably herein as a “season”). Once the season ends withbroadcast of the last one of the series of media content events, thereis typically a break, or relatively long duration in time, before thestart of the next new season. Some embodiments are configured toautomatically modify a timer 144 that is configured to record serialtype media content events. Here, after a currently broadcasting mediacontent event of the series is broadcast, the start date of the timer144 is updated to the next scheduled broadcast date of the next episodein the series. This update information may be communicated to the mediadevice in any suitable manners, such as in the meta data of the mediacontent event and/or in EPG information updates. When the last episodeof a series (referred to as the “season finale”) is broadcast, the dateof broadcast of the first episode of the next series is preferably usedto update that timer 144. If the season finale is also the very lastepisode of a concluding series (referred to as the “series finale”),then there will be no update of the start date or that timer 144. Atsome point in time, the current date will exceed the start date of thetimer 144 by the user defined or predefined duration, and the timer 144will be automatically deleted by the stale timer management system 100.

If the media content event is a onetime event, such as a sporting event,movie, or the like, then the start date of the timer 144 is notautomatically updated. At some point in time, the current date willexceed the start date of the timer 144 by the user defined or predefinedduration, and that particular timer 144 will be automatically deleted bythe stale timer management system 100.

The third example stale timer criteria 300 is the user subscriptioninformation and/or authorization 306. Here, an example timer attributeof a media content event that is scheduled for recording is whether ornot the media content event is a premium-type media content event. Ifthe media content event is a premium-type media content event, the usermust be an authorized subscriber for that particular media content eventat the time of broadcast and recording. That is, the stale timercriteria is a user authorization to record the media content event thatis valid when current date and reaches the start date and start time ofthe timer. The timer attribute is whether the media content event is apremium-type media content event, and therefore requires the valid userauthorization, or if the media content event is a non-premium-type mediacontent event that does not require the valid user authorization.

Some premium-type media content events are provided on a for-pay basis.Here, the user must make payment arrangements for that particularpremium-type media content event. Alternatively, or additionally, apremium-type media content event may be provided by a subscription-basedpremium media content provider (via a particular channel of mediacontent and/or via a particular media content stream 104). Here, theuser must be a paying subscriber that has a current valid authorizationto record the particular media content event of interest at the time ofrecording.

The authorization of a user to receive and/or record a premium-typemedia content event may be stored in the miscellaneous information of atimer 144 (or in another suitable location in the timer 144). If theuser is authorized, the media device 102 records the broadcastingpremium-type media content event. Otherwise, the media device 102 cannotrecord the broadcasting premium-type media content event.

In some situations, information identifying the media content event asbeing a premium-type media content event is stored in the timerinformation. At the time of recording, the stale timer management system100 may be configured to verify authorization of the user. If the useris authorized, the media device 102 records the broadcastingpremium-type media content event.

Situations may arise wherein a user was an authorized subscriber at thetime that the timer 144 was generated for recording of a particularpremium-type media content event. However, at the time of broadcast ofthe premium-type media content event, the user may no longer be asubscriber for that particular subscription-based premium-type mediacontent provider, and/or the pay for view rights for the premium-typemedia content event may have expired. For example, the user may have seta series or repeating timers to record new episodes of a popular program“Spiders” that is airing weekly over the next three months on a premiumtype subscription-based channel. However, at some point, the user mayhave terminated their subscription for service from that particularsubscription-based media content provider, and is therefore no longerauthorized to receive and record any later broadcast “Spider” episodes.However, the previously defined timer 144 for that particular mediacontent event will still be stored in the timer data 136. Here,embodiments of the stale timer management system 100 access theinformation of the timer data 136, or access information in the EPGinformation 132, or access other information, which indicates whetherthe media content event associated with a particular timer requires userauthorization prior to, or at the time of, recording. If userauthorization is required, and the user is properly authorized to recordthe media content event, then the stale timer management system 100determines that timer 144 is an active timer (such that the mediacontent event is recorded during its broadcast that is received at themedia device 102). However, if the user is not properly authorized, thenthe stale timer management system 100 determines that the timer 144 forthat particular media content event is a stale timer. The stale timermay then be automatically deleted by the stale timer management system100 from the timer data 136.

In an example embodiment, the remote timer management system 154 maycommunicate an instruction to the media device 102 to automaticallydelete any timers 144 associated with premium-type media content eventsand/or any timer that are associated with media content events provideby a premium-type media content provider. In response to receiving suchan instruction at the media device 102, the stale timer managementsystem 100 accesses all stored timers 144, defines any found timers 144associated with the premium-type media content events as being a staletimer, and then deletes those stale timers.

The fourth example stale timer criteria 300 is the predefined mediacontent information 308. Here, at some point, a particular media contentevent (or series of media content events) may become known to be notscheduled for broadcast. For example, the media content provider, theoriginating entity that created or produces the media content event (orseries of media content events), may know that that particular mediacontent event (or series of media content events) will never again bebroadcast (or at least broadcast in the foreseeable future), such aswhen the particular media content event (or series of media contentevents) are canceled. This information may then be communicated to themedia device 102. The media device 102 then checks the stored timers 144to determine if a particular timer 144 has been generated and stored forthat particular media content event (or series of media content events).If a timer 144 is found for that particular media content event (orseries of media content events), that that timer may be defined as astale timer and may then be automatically deleted by the stale timermanagement system 100. In a non-limiting exemplary embodiment, the flagor other indicator in the “Stale” column 214 that indicates whether amedia content event may be set to a stale state. Then, when the staletimer management system 100 compares the stale timer criteria with thetimers 144, the identified stale timer may be automatically deleted bythe stale timer management system 100. Alternatively, the stale timermay be automatically deleted in response to receiving information thatthe timer 144 is now stale.

The information that a particular timer 144 has become stale may becommunicated to the media device 102 in a variety of manners. Forexample, but not limited to, the information may be communicated fromthe remote timer management system 154 to the media device 102 via thecommunication system 156. Alternatively, or additionally, theinformation may be included in a media content stream 104, such as inthe metadata of a broadcasting media content event, or as separatelycommunicated information. Here, many receiving media devices 102 willreceive the information. Alternatively, or additionally, the informationmay be included in an EPG information update so that many receivingmedia devices 102 will receive the information. Any suitable manner ofcommunicating the information that a media content event (or series ofmedia content events) has become stale to the media device 102 may beused by the various embodiments.

The information that a media content event (or series of media contentevents) has become stale may be communicated to the media device 102 attimes selected by the remote timer management system 154 (here, referredto as “pushing” the information to the media device 102). Alternatively,or additionally, the media device 102 may communicate a request toreceive the information to the remote timer management system 154 (here,referred to as “pulling” the information), via the communication system156.

The fifth example stale timer criteria 300 is the predefined mediacontent event identifier 310. Here, the identifier informationassociated with a media content event (or series of media contentevents) is used by the stale timer management system 100 to determinewhether the timer 144 has become stale, and accordingly, should beautomatically deleted by the stale timer management system 100. In anexample situation, the remote timer management system 154 maycommunicate an instruction that any timers 144 corresponding to aparticular media content event (or series of media content events) hasbecome stale to the media device 102 are to be deleted. The instructionmay optionally specify that the timers 144 should be automaticallydeleted on a specific date (and optionally, a specific time). Forexample, a particular service provider may change availability of aparticular sporting event to a premium-type media content event. Theinstruction may cause all previously generated and stored timers 144 forthat particular premium-type media content event to be deleted (unlessthe user of that media device is authorized to receive and record thatparticular media content event).

In some embodiments, deleted stale timers (or information correspondingthereto) are copied and are then communicated from the media device 102to the remote timer management system 154. The remote timer managementsystem 154 maintains a database of deleted timers 144 and theirassociated media devices 102. In a non-limiting application, at somepoint in the future, the associated media content event (or series ofmedia content events) may become scheduled to be broadcast to the mediadevices 102. The timers 144 associated with that particular mediacontent event (or series of media content events) may then becommunicated back to those media devices 102 that had previously deletedthose timers 144. The media devices 102 may re-save the timers 144 suchthat when the media content event (or series of media content events) isbroadcast, the media device 102 records the broadcasting media contentevent (or series of media content events). In some embodiments, thetimer listing 158 or other suitable user interface is presented to theuser wherein the user is then able to confirm that the returned timers144 are to be re-saved by their media device 102.

In another non-limiting application, a user may have unsubscribed to apremium-type channel or to a premium-type media content event. At thattime, the associated timers 144 would be have been automatically deletedby the stale timer management system 100. However, at a later time, theuser may have re-subscribed to the premium-type channel and/or to thepremium-type media content event(s). The timers 144 associated with thatparticular premium-type channel and/or to the premium-type media contentevent(s) may then be communicated back to the media device 102. Themedia devices 102 may re-save the timers 144 such that when thepremium-type media content event (or series of media content events) isbroadcast, the media device 102 records the broadcasting premium-typemedia content event (or series of media content events). In someembodiments, the timer listing 158 or other suitable user interface ispresented to the user wherein the user is then able to confirm that thereturned timers 144 are to be re-saved by their media device 102.

In some embodiments, deleted stale timers may be saved into the memory118 or may be retained as information in the timer data 136 (andidentified as being stale). In the event that the stale timers arereactivated as described herein, the detailed information of the staletimers is readily available at the media device 102. Thus, the amount ofinformation stored at the remote timer management system 154, and/or theamount of timer information that is returned by the remote timermanagement system 154 to the media devices 102, may be reduced. Forexample, subscription information for a user of a particular mediadevice 102 may be communicated to the media device 102, and the staletimer management system 100 residing in the media device 102 canreactivate any associated stale timers that have not yet beenautomatically deleted by the stale timer management system 100 based onanother criteria.

It should be emphasized that the above-described embodiments of thestale timer management system 100 are merely possible examples ofimplementations of the invention. Many variations and modifications maybe made to the above-described embodiments. All such modifications andvariations are intended to be included herein within the scope of thisdisclosure and protected by the following claims.

The invention claimed is:
 1. A method of managing timers that controlrecording of at least one of a plurality of media content events by amedia device, the method comprising: retrieving a timer attributeassociated with a timer, wherein the timer is one of a plurality oftimers stored at the media device, wherein each timer is defined by aplurality of timer attributes, wherein the plurality of timer attributesinclude at least an identifier of a media content event that is to berecorded, a start time and date that initiates a recording of the mediacontent event when a current real time and date reaches the start timeand date, and an end time and date that concludes the recording of themedia content event when the current real time and date reaches the endtime and date; comparing the retrieved timer attribute with acorresponding stale timer criteria; and automatically deleting the timerassociated with the retrieved timer attribute when the comparedretrieved timer attribute corresponds to the stale timer criteria,wherein automatically deleting the timer comprises: automaticallydeleting the timer in response to determining that the timer has beenstored at the media device for longer than a duration, wherein theduration is the stale timer criteria, and wherein the duration isdefined by at least one of a user of the media device or that iscommunicated to the media device from a remote timer management systemthat is communicatively coupled to the media device; automaticallydeleting the timer in response to determining that the timer has anidentifier that corresponds to a specified identifier, wherein thespecified identifier is the stale timer criteria, wherein the specifiedidentifier identities one of a plurality of media content events, andwherein the specified identifier has been communicated to the mediadevice from the remote timer management system; automatically deletingthe timer in response to determining that the timer has a seriesidentifier that corresponds to a specified series identifier, whereinthe specified series identifier is the stale timer criteria, wherein thespecified series identifier identifies a series of media content events,and wherein the specified series identifier has been communicated to themedia device from the remote timer management system; and automaticallydeleting the timer in response to determining that the timer isassociated with an expired subscription, wherein the user's accessrights to a subscription service associated with the expiredsubscription has expired, wherein the expired subscription is the staletimer criteria, wherein information identifying the expired subscriptionhas been communicated to the media device from the remote timermanagement system, and wherein the expired subscription informationidentifies the media device as currently being unauthorized to record atlast one of the plurality of media content events provided to the mediadevice by a content provider associated with the expired subscription.2. The method of claim 1, wherein the retrieved timer attributeassociated with the timer is one of the start time and date thatinitiates the recording of the media content event or the end time anddate that concludes the recording of the media content event, the methodfurther comprising: determining a difference between the current realtime and date and one of the start time and date or the end time anddate; comparing the determined difference with the duration; andautomatically deleting the timer associated with the retrieved timerattribute only when the determined difference exceeds the duration. 3.The method of claim 1, wherein the retrieved timer attribute associatedwith the timer is an identifier of the media content event that is to berecorded by the media device, the method further comprising: comparingthe specified identifier with the identifier of the media content eventthat is to be recorded by the media device; and automatically deletingthe timer associated with the retrieved timer attribute only when thespecified identifier is the same as the identifier of the media contentevent that is to be recorded by the media device.
 4. The method of claim1, wherein the media content event that is to be recorded by the mediadevice in a member of the series of media content events such that themedia content event to be recorded is associated with the seriesidentifier, the method further comprising: comparing the specifiedseries identifier with the series identifier of the media content eventthat is to be recorded by the media device; and automatically deletingthe timer associated with the retrieved timer attribute only when thespecified series identifier is the same as the series identifier of themedia content event that is to be recorded by the media device.
 5. Themethod of claim 1, wherein the plurality of timers were stored into amemory of the media device prior to retrieving the timer, and whereindeleting the timer comprises: deleting the timer from the memory of themedia device.
 6. The method of claim 1, wherein the media device storesthe plurality of timers, wherein each of the timers is configured torecord one of the plurality of media content events as they arereceivable at the media device, the method further comprising:communicating a request from the media device to the remote timermanagement system, wherein the request is to receive stale timercriteria information; receiving the stale timer criteria informationfrom the remote timer management system in response to communicating therequest; and comparing the received stale timer criteria informationwith the timer attributes of each one of the stored plurality of timersin response to receiving the stale timer criteria information, whereinthe stale timer criteria information comprises at least one of thespecified identifier that identifies one of the plurality of mediacontent events, the specified series identifier that identifies theseries of media content events, and the expired subscription informationthat identifies the media device as being unauthorized to record atleast one of the plurality of media content events.
 7. The method ofclaim 1, wherein the media device stores the plurality of timers,wherein each of the timers is configured to record one of the pluralityof media content events as they are receivable at the media device, themethod further comprising: periodically receiving stale timer criteriainformation from the remote timer management system; and comparing thereceived stale timer criteria information with the timer attributes ofeach one of the stored plurality of timers in response to receiving thestale timer criteria information, wherein the stale timer criteriainformation comprises at least one of the specified identifier thatidentifies one of the plurality of media content events, the specifiedseries identifier that identifies the series of media content events,and the expired subscription information that identifies the mediadevice as being unauthorized to record at least one of the plurality ofmedia content events.
 8. The method of claim 1, further comprising:communicating first information corresponding to at least oneautomatically deleted timer from the media device to the remote timermanagement system, wherein the remote timer management system determineswhether the media content event associated with the deleted timer isrescheduled for a future broadcast to the media device during at leastone future broadcast time and date; receiving information at the mediadevice from the remote timer management system that indicates that themedia content event associated with the deleted timer is rescheduled forthe future broadcast to the media device; and receiving a userspecification to generate and store a new timer that will record themedia content event associated with the deleted timer at the at leastone rescheduled future broadcast time and date.
 9. A method of managingtimers that control recording of at least one of a plurality of mediacontent events by a media device, the method comprising: retrieving atimer attribute associated with the timer, wherein the timer is one of aplurality of timers stored at the media device, wherein each timer isdefined by a plurality of timer attributes, wherein the plurality oftimer attributes include at least an identifier of a media content eventthat is to be recorded, a start time and date that initiates a recordingof the media content event when a current real time and date reaches thestart time date, and an end time and date that concludes the recordingof the media content event when the current real time and date reachesthe end time and date; comparing the retrieved timer attribute with acorresponding stale timer criteria, wherein the stale timer criteriacomprises at least one selected from a group consisting of: a durationdefined by at least one of a user or that is communicated to the mediadevice from a remote timer management system that is communicativelycoupled to the media device; a specified identifier that identifies oneof a plurality of media content events that is communicated to the mediadevice from the remote timer management system; a specified seriesidentifier that identifies a series of media content events that iscommunicated to the media device from the remote timer managementsystem, wherein the name of the series is associated with a number ofthe plurality of media content events; and subscription informationcommunicated to the media device from the remote timer managementsystem, wherein the subscription information identifies the media deviceas being authorized to record at least one of the plurality of mediacontent events provided to the media device by a content providerassociated with the subscription information; and automatically deletingthe timer associated with the retrieved timer attribute when thecompared retrieved stale timer criteria corresponds to the stale timercriteria, wherein the retrieved timer attribute associated with thetimer is first subscription information associated with the mediacontent event that is to be recorded by the media device, wherein thesubscription information communicated to the media device from theremote timer management system is second subscription information, themethod further comprising: comparing the first subscription informationwith the second subscription information; and automatically deleting thetimer associated with the retrieved timer attribute only when the firstsubscription information is the same as the second subscriptioninformation.
 10. The method of claim 9, wherein the first subscriptioninformation identifies the media content event that is to be recorded bythe media device as a premium-type media content event, and wherein thesecond subscription information authorizes the media device to presentor record the premium-type media content event.
 11. The method of claim9, wherein the first subscription information identifies the mediacontent event that is to be recorded by the media device as beingprovided by a subscription-based premium media content provider, andwherein the second subscription information authorizes the media deviceto present or record the media content event when provided to the mediadevice by the subscription-based premium media content provider.
 12. Amedia device configured to record a broadcasted media content event at atime of its broadcast, comprising: a tuner configured to tune to andreceive a broadcast media content stream having the media content eventthat is to be recorded; a memory that stores a plurality of timers,wherein each timer is defined by a plurality of timer attributes thatinclude at least an identifier of the media content event that is to berecorded, a start time and date that initiates a recording of the mediacontent event when a current real time and date reaches the start timeand date, and an end time that concludes the recording of the mediacontent event when the current real time reaches the end time, arecording medium operable to receive and store the media content eventduring the broadcast of the media content event that is to be recorded;and a processor system, wherein the processor system is configured to:retrieve a timer attribute associated with a timer; compare theretrieved timer attribute with a corresponding stale timer criteria;automatically delete the timer associated with the retrieved timerattribute when the compared retrieved stale timer criteria correspondsto the stale timer criteria, wherein the processor is further configuredto: automatically delete the timer in response to determining that thetimer has been stored at the media device for longer than a duration,wherein the duration is the stale timer criteria, and wherein theduration is defined by at least one of a user of the media device orthat is communicated to the media device from a remote timer managementsystem that is communicatively coupled to the media device;automatically delete the timer in response to determining that the timerhas an identifier that corresponds to a specified identifier, whereinthe specified identifier is the stale timer criteria, wherein thespecified identifier identifies one of a plurality of media contentevents, and wherein the specified identifier has been communicated tothe media device from the remote timer management system; automaticallydelete the timer in response to determining that the timer has a seriesidentifier that corresponds to a specified series identifier, whereinthe specified series identifier is the stale timer criteria, wherein thespecified series identifier identifies a series of media content events,and wherein the specified series identifier has been communicated to themedia device from the remote timer management system; and automaticallydelete the timer in response to determining that the timer is associatedwith an expired subscription wherein the user's access rights to asubscription service associated with the expired subscription hasexpired, wherein the expired subscription is the stale timer criteria,wherein information identifying the expired subscription has beencommunicated to the media device from the remote timer managementsystem, and wherein the expired subscription information identifies themedia device as currently being unauthorized to record at least one ofthe plurality of media content events provided to the media device by acontent provider associated with the expired subscription.
 13. The mediadevice of claim 12, wherein the retrieved timer attribute associatedwith the timer is one of the start time and date that initiates therecording of the media content event or the end time and date thatconcludes the recording of the media content event, and wherein theprocessor system is further configured to: determine a differencebetween the current real time and date and one of the start time anddate or the end time and date; compare the determined difference withthe duration; and automatically delete the timer associated with theretrieved timer attribute only when the determined difference exceedsthe duration.
 14. The media device of claim 12, wherein the retrievedtimer attribute associated with the timer is an identifier of the mediacontent event that is to be recorded by the media device, and whereinthe processor system is further configured to: compare the specifiedidentifier with the identifier of the media content event that is to berecorded by the media device; and automatically delete the timerassociated with the retrieved timer attribute only when the specifiedidentifier is the same as the identifier of the media content event thatis to be recorded by the media device.
 15. The media device of claim 12,wherein the media content event that is to be recorded by the mediadevice in a member of the series of media content events such that themedia content event to be recorded is associated with the seriesidentifier, and wherein the processor system is further configured to:compare the specified series identifier with the series identifier ofthe media content event that is to be recorded by the media device; andautomatically delete the timer associated with the retrieved timerattribute only when the specified series identifier is the same as theseries identifier of the media content event that is to be recorded bythe media device.
 16. The media device of claim 12, wherein theprocessor system is further configured to: communicate a request fromthe media device to the remote timer management system, wherein therequest is to receive stale timer criteria information; receive thestale timer criteria information from the remote timer management systemin response to communicating the request; and compare the received staletimer criteria information with the timer attributes of each one of thestored plurality of timers in response to receiving the stale timercriteria information, wherein the stale timer criteria informationcomprises at least one of the specified identifier that identities oneof the plurality of media content events, the specified seriesidentifier that identifies the series of media content events, and theexpired subscription information that identifies the media device asbeing unauthorized to record at least one of the plurality of mediacontent events.
 17. The media device of claim 12, wherein the processorsystem is further configured to: communicate an automatically deletedtinier from the media device to the remote timer management system,wherein the remote timer management system determines whether the mediacontent event associated with the deleted timer is rescheduled for afuture broadcast to the media device during at least one futurebroadcast time and date; receive information at the media device fromthe remote timer management system that indicates that the media contentevent associated with the deleted timer is rescheduled for the futurebroadcast to the media device; and receive a user specification togenerate and store a new timer that will record the media content eventassociated with the deleted timer at the at least one rescheduled futurebroadcast time and date.
 18. A media device configured to record abroadcasted media content event at the time of its broadcast,comprising: a tuner configured to tune to and receive a broadcast mediacontent stream having the media content event that is to be recorded; amemory that stores a plurality of timers, wherein each timer is definedby a plurality of timer attributes that include at least an identifierof the media content event that is to be recorded, a start time and datethat initiates a recording of the media content event when a currentreal time and date reaches the start time and date, and an end time thatconcludes the recording of the media content event when the current realtime reaches the end time, a recording medium operable to receive andstore the media content event during the broadcast of the media contentevent that is to be recorded; and a processor system, wherein theprocessor system is configured to: retrieve a timer attribute associatedwith a timer; compare the retrieved timer attribute with a correspondingstale timer criteria, wherein the stale timer criteria comprises atleast one selected from a group consisting of: a duration defined by atleast one of a user or that is communicated to the media device from aremote timer management system that is communicatively coupled to themedia device; a specified identifier that identifies one of a pluralityof media content events that is communicated to the media device fromthe remote timer management system; a specified series identifier thatidentifies a series that is communicated to the media device from theremote timer management system, wherein the name of the series isassociated with a number of the plurality of media content events; andsubscription information communicated to the media device from theremote timer management system, wherein the subscription informationidentifies the media device as being authorized to record at least oneof the plurality of media content events provided to the media device bya content provider associated with the subscription information; andautomatically delete the timer associated with the retrieved timerattribute when the compared retrieved stale timer criteria correspondsto the stale timer criteria, wherein the retrieved timer attributeassociated with the timer is first subscription information associatedwith the media content event that is to be recorded by the media device,wherein the subscription information communicated to the media devicefrom the remote timer management system is second subscriptioninformation, and wherein the processor system is further configured to:compare the first subscription information with the second subscriptioninformation; and automatically delete the timer associated with theretrieved timer attribute only when the first subscription informationis the same as the second subscription information.
 19. The media deviceof claim 18, wherein the first subscription information identifies themedia content event that is to be recorded by the media device as apremium-type media content event, and wherein the second subscriptioninformation authorizes the media device to present or record thepremium-type media content event.
 20. The media device of claim 18,wherein the first subscription information identifies the media contentevent that is to be recorded by the media device as being provided by asubscription-based premium media content provider, and wherein thesecond subscription information authorizes the media device to presentor record the media content event when provided to the media device bythe subscription-based premium media content provider.